Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
Medway Council

Tree preservation zone

There is a problem

  • 91 entries must have dates in YYYY-MM-DD format

entity: 19130929

reference
New TPO - To be confirmed
name
tree-preservation-order
tree-preservation-zone-type
geometry
MULTIPOLYGON (((0.489597 51.389635,0.489592 51.389626,0.489600 51.389619,0.489621 51.389626,0.489610 51.389637,0.489597 51.389635)),((0.489566 51.389658,0.489562 51.389645,0.489587 51.389646,0.489585 51.389656,0.489566 51.389658)),((0.489385 51.389570,0.489375 51.389560,0.489380 51.389552,0.489399 51.389549,0.489412 51.389559,0.489405 51.389569,0.489385 51.389570)),((0.489044 51.389754,0.489040 51.389746,0.489051 51.389739,0.489069 51.389748,0.489058 51.389757,0.489044 51.389754)))
point
POINT (0.4894 51.389632)
notes
entry-date
2026-05-09
start-date

start-date must be a real date

end-date

How to fix this issue

Your dataset is missing the start-date column.

The Tree preservation zone guidance explains how to fix the issue:

start-date

The date that the tree preservation order came into force, written in YYYY-MM-DD format.

Example: 1984-03-28

How to improve Medway Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL